Internetworking For Circuit Switched Fallback-Network Initiated USSD Request/Notification Procedure Mobile-Terminated Location Request Procedure Provide Subscriber Information Procedure

ABSTRACT

A method for switch user equipment from a Long Term Evolution system to a Circuit Switched system when receiving a voice call is disclosed. The method may comprise: receiving, at an IWF (Internet Working Function) network node, a Mobility Application Part Unstructured Supplementary Service Data (MAP USSD) message identifying a User Equipment (UE) originated from a USSD application, the UE associated with a first Mobile Switching Center (MSC); initiating Circuit Switched Fallback (CSFB) by sending a paging request to the UE; receiving a Cancel Location message associated with the UE from a Home Location Register (HLR) indicative of the UE being associated with a second MSC; forwarding the MAP USSD message to the UE via the HLR and the second MSC; receiving a MAP USSD response message from the UE via the HLR; and forwarding the MAP USSD response message to the USSD application.

FIELD

The present disclosure relates the field of telecommunications, and moreparticularly to internetworking for circuit switched fallback.

BACKGROUND

Currently, Long Term Evolution (LTE) systems do not support voice calls,so Circuit Switched Fallback (CSFB) specified by 3GPP standards TS23.272is executed for these calls. CS fallback function and SMS (short messagesystem) message delivery via the CS core network is realized by reusingGs interface mechanisms as defined in 3GPP TS 29.018 on the interfacebetween the MME (Mobility Management Entity) in the EPS (Evolved PacketSystem) and the VLR (Visitor Location Register). This interface iscalled the SGs interface.

For example, the network is enhanced to page the mobile over the LTEradio, and when a mobile camped on LTE radio receives a voice call pagerequest over the LTE system, the mobile device falls back to the CSradio to receive voice call. In connection with CSFB, any active datasession is suspended or handed over to 2G/3G PS (packet switched)access. For Mobile Originating (MO) calls, the mobile devices or userequipment (UE) camped on the LTE radio initiate fallback on their own tooriginate a voice call in the CS domain. Mobiles camped on LTE radio cansend and receive SMS messages without falling back. The basic idea is toforce the UE to fallback to CS radio for voice calls, which is not VoLTE(Voice Over LTE). In order to execute the CSFB, a new interface, calledSGs, is required between MME (Mobility Management Entity) and MSC/VLR(Mobile Switching Center/Visitor Location Register) to allow the MSC toknow when a UE is EPC (Evolved Packet Core) attached. The MSC/VLRregisters with the HLR (Home Location Register) as normal, so thatMobile Terminating (MT) voice calls and SMS messages are routed there.In these cases, MO/MT SMS messages are delivered over LTE access and EPCvia the MSC. For MO calls, the UE falls back to CS radio beforeoriginating the call so no core network changes are required. For MTcalls, the call is delivered to the MSC as normal, and the MSC pages theUE via the new SGs interface between the MME and the MSC. The UE fallsback to CS radio and issues either a Location Update or Page Response.The MSC completes the call. If the UE falls back to a MSC different thanthe one that issued the SGs page, complex “roaming retry” procedures arerequired to complete the call. That said, this process requires newinterfaces and modification of existing nodes in each of the LTE and CSsystems. The new SGs interface is required between the MSC in the CScore network and the MME in the EPC. The SGs enables the MSC to learn ofEPC attachment, MO/MT SMS during EPC attachment, and MSC to page thesubscriber over EPC and LTE access for voice calls. As for the modifiednodes, the MSC requires SGs interface and associated state machine. TheMME requires an SGs interface and modification of the associated statemachine and requires S3 interface to SGSN if ISR (Idle mode SignalingReduction) is enabled. The MSC/HLR/GMSC all require changes in order tosupport Roaming Retry, which is made more likely by CSFB.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified block diagram of an embodiment of a communicationsystem for circuit switched fallback;

FIGS. 2A-2I are simplified block diagrams of embodiments ofcommunication systems illustrating signaling during circuit switchedfallback;

FIGS. 3A and 3B is call flow diagram illustrating an embodiment of acircuit switched fallback procedure;

FIG. 4 is a flow chart illustrating example method for executing circuitswitched fallback;

FIG. 5 is a call flow diagram illustrating an embodiment of a newnetwork initiated USSD request procedure;

FIG. 6 is a simplified block diagram of an exemplary embodiment of acommunication system;

FIG. 7 is a call flow diagram illustrating an embodiment of a new mobileterminating location report procedure (MT-LR); and

FIG. 8 is a call flow diagram illustrating an embodiment of a newprovide subscriber information, fallback to CS procedure.

DETAILED DESCRIPTION

FIG. 1 is an example communication system 100 for switching UserEquipment (UE) from a Long Term Evolution (LTE) system to a CircuitSwitched (CS) system when receiving a voice call. For example, when theUE is camped on an LTE system and receives an indication of a mobileterminating voice call from the CS domain, the UE may switch to a CSnetwork (2G or 3G) to accept the call. In general, switching from theLTE network to the CS network for voice calls is referred to as CircuitSwitched Fall Back (CSFB). In some implementations, the system 100 mayexecute CSFB independent or without including an SGs interface on aMobile Switching Center (MSC). In addition, the system 100 may executethe CSFB independent or without modifying the existing MSC. For example,the system 100 may include a CSFB Internetworking Function (IWF) 102(discussed in more detail below) that connects to a CS network throughMAP interfaces and connects to an LTE network through an SGs interface.In doing so, the system 100 may eliminate, reduce or otherwise preventthe following: changes at the MSC (e.g., no SGs interfaces at the MSC,no configuration changes); roaming retry (e.g., saves on complex MSC/HLRfunctionality, reduces call setup delay); TA to LA mapping (e.g., allTAs may be mapped to a single LA, owned by the CSFB IWF); processing theMT call bearer (e.g., no bearer trunks, reduce cost); and/or others.

At a high level, the system 100, in some implementations, includes theCSFB IWF 102 communicably coupled to a CS system 104, an LTE system 106,and UE 108 through the networks 104 and 106. The CS system 104 includesa radio access network (RAN) 110 and a cellular core network 112, andthe LTE system 106 includes an LTE Radio Access Network 114 such asevolved UTRAN (E-UTRAN 114) and a core network 116 called an EvolvedPacket Core (EPC) 116. The cellular core network 112 includes the GMSC118, the HLR 120, the MSC/VLR 122, and the SGSN 124. The EPC 116includes the MME 126 and the Home Subscriber Server (HSS) 128. As for ahigh level description, the CSFB IWF 102 registers with the servingMSC/VLR when the UE performs an IMSI attach over EPC 116. Afterregistration, the GMSC 118 may receive an incoming request to terminatea voice call with the UE and transmit a request for routing informationto the HLR 120. After determining that the CSFB IWF 102 is presented asthe serving MSC to the cellular core network 112, the HLR 120 maytransmit a request for the MSRN to the CSFB IWF 102. In connection withstoring information identified with the request, the CSFB IWF 102transmits a request to the UE 108 through the MME 126 of the EPC 116 tofall back to the cellular system 104. The UE 108 may transmit a requestto the MSC/VLR 122 through the RAN 110 to update its location, which isrelayed to the HLR 120. The HLR 120 re-assigns the MSC/VLR 122 as theserving MSC and transmits a Cancel Location request to the CSFB IWF 102.The CSFB IWF 102 sends a new request for routing information to the HLR120 and transmits the received MSRN in the PRN Ack to the GMSC 118,which uses this MSRN to route the call to the MSC/VLR 122 where it iscompleted.

Turning to more detailed description of the system 110, the CSFB IWF 102can include any software, hardware, and/or firmware operable to transfera UE 108 from the LTE system 106 to the CS system 104 in connection withreceiving a mobile terminating request for a voice call from thecellular core network 112. For example, the CSFB IWF 102 may page the UE108 to request an update location request with the HLR 120 in thecellular core network 112. By updating the location in the cellularsystem 104, the CSFB IWF 102 may reply to the PRN request using the MSRNthat the cellular system 104 assigns during the location update. Ininitiating the updated location, the CSFB IWF 102 may initiate the UE108 to fallback to CS radio for voice calls, which is not Voice over LTE(VoLTE). In some implementations, the CSFB IWF 102 can include a newinterface (SGs) to MME 126, which may allow the CSFB IWF 102, whenoperating as the MSC/VLR, to determine when a UE 108 is attached to theEPC 116. The CSFB IWF 102 may include interfaces such as SGs to MME 126,MAP to HLR 120, MAP to SMSC, and/or others. As for the SGs to MME 126,the CSFB IWF 102 may execute standard SGs functionality, and/or the MME126 may identify the CSFB IWF 102 as a Visitor Location Register (VLR).In other words, the CSFB IWF 102 may support the SGs interface from theMME 126 in the EPC domain. In these instances, the CSFB IWF 102 mayappear as a VLR to the MME 126. The CSFB IWF 102 acting as VLR/MSC forthe subscribers in EPC domain may interact with the HLR 120 over a MAPinterface and also with an SMSC in the network 112 for SMS relatedprocedures. The CSFB IWF 102 may contain a “VLR” that maintains the SGsstates and state machine defined in 3GPP TS 29.118. As for the MAP toHLR 120, the CSFB IWF 102 may execute location updating proceduresand/or call routing procedures using this interface. The MAP interfacebetween the CSFB IWF 102 and HLR 1020 may be used for locationmanagement, subscriber management and/or call handling procedures. Asfor the MAP to SMSC, the CSFB IWF 102 may execute MO/MT SMS proceduresusing MAP MO Forward Short Message and/or MAP MT Forward Short Message.For example, the MAP interface between CSFB IWF 102 and an SMSC may beused for mobile originated and/or mobile terminated SMS. In someimplementations, the CSFB IWF 102 may operate independent or withoutbearer facilities (e.g., TDM trunks). The CSFB IWF 102 may execute oneor more of the following: receive the MT call signaling from the HLR120, as it appears as the serving MSC/VLR; sends SGs Paging Request totrigger CSFB; initiate MT call signaling to redirect the call to the new(and real) serving MSC/VLR; and/or other functions. In connection withthese processes, the UE 108 may fall back to the CS domain and mayperform a Location Update MSC/VLR 122. In addition, the UE 108 mayaccept the call once the CSFB IWF 102 redirects it. As previouslymentioned, the CSFB IWF 102 may, in some implementations, emulate orotherwise represent itself as an element of core network 112. Forexample, the CSFB IWF 102 may emulate or otherwise represent itself asan MSC, a VLR, or other element of the cellular core network 112. In thecase that communication node 108 emulates an MSC, the CSFB IWF 102 maybe queried by the HLR 120 in the cellular core network 112 like anyother MSC.

Turning to a detailed description of other elements in the system 100,the LTE system 106 can includes the EPC 116 and the E-UTRAN 114. The EPC116 provides connectivity to an external network such as the cellularcore network 112. The EUTRAN 114 includes one or more base stations suchas eNode-B (eNB) base stations that provide wireless service(s) to UE108. An EPC-based core network can include a Serving Gateway (SGW), theMME 126, and a Packet Gateway (PGW). An SGW can route traffic within theEPC 116. The MME 155 is responsible for core-network mobility control,attachment of the UE 108 to the core network and for maintaining contactwith idle mode UEs. The PGW is responsible for enabling theingress/egress of traffic from/to the Internet. The PGW can allocate IPaddresses to the UEs 108.

An LTE-based wireless communication system has network interfacesdefined between system elements. The network interfaces include the Uuinterface defined between a UE and an eNB, the S1U user-plane interfacedefined between an eNB and an SGW, the S1C control-plane interfacedefined between an eNB and an MME (also known as S1-MME), and the S5/S8interface defined between an SGW and a PGW. Note that the combination ofS1U and S1C is often simplified to “S1.”

MME 126 is a control-node for the LTE access network. The MME 126 isresponsible for UE 108 tracking and paging procedures includingretransmissions. MME 126 handles the bearer activation/deactivationprocess and is also responsible for choosing the SGW for a UE 108 at theinitial attach and at the time of an intra-LTE handover. The MME 126also authenticates the user by interacting with the HSS 124. The MME 126also generates and allocates temporary identities to UEs and terminatesNon-Access Stratum (NAS) signaling. The MME 126 checks the authorizationof the UE 108 to camp on the service provider's Public Land MobileNetwork (PLMN) and enforces UE roaming restrictions. The MME 126 is thetermination point in the network for ciphering/integrity protection forNAS signaling and handles the security key management. Lawfulinterception of signaling is also supported by the MME 126. The MME alsoprovides the control plane function for mobility between LTE and 2G/3Gaccess networks with the S3 interface terminating at the MME 126 fromthe SGSN 130. The MME 126 also terminates the S6a interface towards thehome HSS 128 for roaming UEs.

The SGW routes and forwards user data packets, while also acting as themobility anchor for the user plane during inter-eNB handovers and as theanchor for mobility between LTE and other 3GPP technologies (terminatingS4 interface and relaying the traffic between 2G/3G systems and PDN GW).For idle state UEs, the SGW terminates the down link data path andtriggers paging when down link data arrives for the UE 108. The SGWmanages and stores UE contexts, e.g., parameters of the IP bearerservice and network internal routing information. The SGW also performsreplication of the user traffic in case of lawful interception. The PGWprovides connectivity to the UE 108 to external packet data networks bybeing the point of exit and entry of traffic for the UE 108. A UE 108may have simultaneous connectivity with more than one PGW for accessingmultiple packet data networks. The P-GW performs policy enforcement,packet filtering for each user, charging support, lawful interception,and packet screening. The PGW also provides an anchor for mobilitybetween 3GPP and non-3GPP technologies such as WiMAX and 3GPP2 (CDMA 1Xand EvDO). The SGW or the PGW depending on the embodiment, can be usedto provide deep packet inspection and provide advertising to the user ona per subscriber basis as described above on a chassis implementing aSGW or a PGW.

The cellular core system 104 typically includes various switchingelements, gateways and service control functions for providing cellularservices. The cellular core system 104 often provides these services viaa number of cellular access networks (e.g., RAN) and also interfaces thecellular system with other communication systems such as EPC 116. Inaccordance with the cellular standards, the cellular core system 104 mayinclude a circuit switched (or voice switching) portion for processingvoice calls and a packet switched (or data switching) portion forsupporting data transfers such as, for example, e-mail messages and webbrowsing. The circuit switched portion includes MSC/VLR 122 thatswitches or connects telephone calls between cellular access system 106and PSTN 104 or another network, between cellular core networks orothers. The MSC/VLR 122 may support only a single media stream (e.g.,single TDM channel for the standard A-interface, single RTP stream forAoIP) towards the RAN 110. This single media stream may be used forsupplementary services which involve multiple calls to/from the mobilesuch as call waiting. In other words, multiple calls to/from a GSMmobile share a single media connection on the MSC's access interface.

The cellular core system 104 a may also include the HLR 120 formaintaining “permanent” subscriber data and a VLR (and/or an SGSN) for“temporarily” maintaining subscriber data retrieved from the HLR 120 andup-to-date information on the location of those UE 108 using a wirelesscommunications method. In addition, the cellular core system 104 mayinclude Authentication, Authorization, and Accounting (AAA) thatperforms the role of authenticating, authorizing, and accounting for UE108 operable to access cellular core system 104. While the descriptionof the core system 104 is described with respect to GSM networks, thecore system 104 may include other cellular radio technologies such asUMTS, CDMA, and others without departing from the scope of thisdisclosure.

RAN 110 provides a radio interface between mobile device 102 a and thecellular core system 104 a which may provide real-time voice, data, andmultimedia services (e.g., a call) to UE 108. In general, RAN 110communicates air frames via radio frequency (RF) links. In particular,RAN 110 converts between air frames to physical link based messages fortransmission through the cellular core system 104 a. RAN 110 mayimplement, for example, one of the following wireless interfacestandards during transmission: GSM access, UMTS access, Code DivisionMultiple Access (CDMA), Time Division Multiple Access (TDMA), GeneralPacket Radio Service (GPRS), Enhanced Data Rates for Global Evolution(EDGE), or proprietary radio interfaces. Users may subscribe to RAN 110,for example, to receive cellular telephone service, Global PositioningSystem (GPS) service, XM radio service, etc.

RAN 110 may include Base Stations (BS) connected to Base StationControllers (BSC) 132. BS receives and transmits air frames within ageographic region of RAN 110 (i.e., transmitted by UE 108) andcommunicates with other UE connected to the cellular core system 104.Each BSC 132 is associated with one or more BS 114 and controls theassociated BS 114. For example, BSC 132 may provide functions such ashandover, cell configuration data, control of RF power levels or anyother suitable functions for managing radio resource and routing signalsto and from BS. MSC/VLR 122 may be connected to BSC 132 through astandard interface such as the A-interface. While the elements of RAN110 are describe with respect to GSM networks, the RAN 110 may includeother cellular technologies such as UMTS, CDMA, and/or others. In thecase of UMTS, the RAN 110 may include Node B and Radio NetworkControllers (RNC).

Turning to a more detailed description of the elements, the UE 108comprises an electronic device operable to receive and transmit wirelesscommunication with system 100. As used in this disclosure, the UE 108 isintended to encompass cellular phones, data phones, pagers, portablecomputers, SIP phones, smart phones, personal data assistants (PDAs),one or more processors within these or other devices, or any othersuitable processing devices capable of communicating information usingcellular radio technology. In the illustrated implementation, the UE 108is able to transmit in one or more cellular band. In these cases,messages transmitted and/or received by the UE 108 may be based on acellular radio technology. There may be any number of the UEs 108communicably coupled to cellular access network 110. Generally, the UE108 may transmit voice, video, multimedia, text, web content or anyother user/client-specific content. In short, the UE 108 generatesrequests, responses or otherwise communicates with mobile core system104 a through RAN 110 or the EPC 116 through the E-UTRAN 114.

In some aspects of operation, the system 100 may execute one or more ofthe following: receiving a Provide Roaming Number (PRN) request from aHome Location Register (HLR) in the CS network for a Mobile StationRoaming Number (MSRN) in connection with mobile terminating callrequest; transmit a request to the UE through the Mobility ManagementEntity (MME) in the LTE system to fall back to the CS system; receive aCancel Location (CL) request from the HLR in connection with thelocation of the UE being reassigned to a different MSC; in response toat least the CL request, transmit a Send Routing Information (SRI)request to the HLR; receive the MSRN from the MSC through the HLR; usingthe received MSRN, transmit a PRN Acknowledgement (PRN Ack) to the HLRsuch that the call terminates with the UE using the MSRN; and/or others.

FIGS. 2A-2I are systems 200-280 illustrating signaling for executingCSFB in accordance with some implementations of the present disclosure.Referring to FIG. 2A, the GMSC 118 receives the signal 202 indicating arequest to terminate a voice call with the UE 108. Referring to FIG. 2B,the system 210 illustrates the signal 212 requesting the MSRN for the UE108. In particular, the GMSC 118 transmits a Provide Roaming Number(PRN) request to the HLR 120, and the HLR 120 transmits the PRN requestto CSFB IWF 102 as the MSC/VLR for the UE 108. Referring to FIG. 2C, thesystem 220 illustrates a signal 222 illustrating a page requesting theUE 108 to update its location with the HLR 120. In particular, the CSFBIWF 102 transmits the page to the MME 126, which, in turn, transmits thepage to the UE 108 through the EUTRAN 114. Referring to FIG. 2D, thesystem 230 illustrates the UE 108 retuning communication form theE-UTRAN 114 to the RAN 110. Referring to FIG. 2E, the system 240illustrates the signal 242 requesting a location update from thecellular core network 112. In particular, the UE 108 transmits an updaterequest to the HLR 120 through the BSC 132 and the MSC/VLR 122.Referring to FIG. 2F, the system 250 illustrates a signal 252 indicatingthat the UE 108 is registered with a different MSC. In particular, theHLR 120 updates registration of the UE 108 with the MSC/VLR 122 andtransmits a Cancel Location (CL) request to the CSFB IWF 102. Referringto FIG. 2G, the system 260 illustrates the signal 262 requesting thecurrent MSRN from the HLR 20. In particular, the CSFB IWF 102 transmitsa SRI request to the HLR 120 using the MSISDN identified in thepreviously PRN request received from the GMSC 118 via the HLR 120.Referring to FIG. 2H, the system 270 illustrates the signal 272 forretrieving MSRN and transmitting the MSRN to the CSFB IWF 102. Inparticular, the HLR 120 identifies the MSC/VLR 122 as the VMSC andretrieves the current MSRN from the MSC/VLR 122. Referring to FIG. 2I,the system 280 illustrates signal 282 transmitting the current MSRN tothe GMSC 118 via HLR 120 to complete the mobile terminating call withthe UE 108.

FIGS. 3A and 3B illustrate a call flow 300 for executing a CSFB inaccordance with some implementations of the present disclosure. In thecall flow 300, the UE 108 initiates the Location Area Update or aCombined RA/LA Update procedure if the LA of the new cell is differentfrom the one stored in the UE 108. The CSFB IWFs are assigned an LAIwhich is mutually exclusive from the ones used in 2G/3G space whichforces the UE 108 to always initiate a Location Area Update. In idlemode, the MME 126 sends Paging request to the eNodeB 114 which in turnsends the request to the UE 108. The MME 126 sends the Service Requestto the CSFB IWF 102 after receiving the Extended Service Request fromthe UE 108. In active mode, the MME 126 sends CS Paging request directlyto the UE 108 as it has an established S1 connection. The MME 126 sendsthe Service Request to the CSFB IWF 102 immediately after sending thePaging Request to the UE 108. In some implementations, the CSFB IWF 02may set the Service Indicator to “CS Call Indicator” in theSGAP-PAGING-REQUEST message. The CSFB IWF 102 may identify this onreceiving MAP PRN message from HLR 120. The CSFB IWF 102 may not includethe following attributes in the SGAP-PAGINGREQUEST as these may not beavailable (e.g., LCS Client Identity, LCS Indicator). The MSC/VLR 122may not receive a Service Request message from the CSFB IWF 102. 3GPP TS23.272 says that Service Request message may be used as a trigger toinform the calling party that the call is progressing and to start theCFNRy timer. The CSFB IWF 102 may follow the standard procedures toinform the call progress. Call progress may be triggered per normalprocedures once the UE falls back to GERAN/U-TRAN and the call is setupthere. Once the CSFB IWF 102 has received a SGsAP-SERVICEREQUEST fromthe MME 122, it may send subsequent page retries. The 2G/3G BSC/MSC maynot receive a Paging Response from the UE 108 as it always performs aLocation Area Update after moving from E-UTRAN 114. The HLR 120 sendsthe MAP CANCEL LOCATION to the old MSC (CSFB IWF 102 in this case) inparallel to handling the MAP UPDATE LOCATION from new MSC/VLR 122. TheCSFB IWF 102 may not wait for the MAP UPDATE LOCATION procedures (whichincludes one or more MAP INSERT SUBSCRIBER DATA messages) to completebefore sending MAP CANCEL LOCATION. The MAP UPDATE LOCATION proceduresfrom the new MSC/VLR 122 at the HLR 120 and the MAP SRI procedures fromCSFB IWF 102 may happen in parallel or at least in connection. The CSFBIWF 102 may not be aware of when the new UPDATE LOCATION is completedand may not wait to send MAP SRI to the HLR 120. The trigger for CSFBIWF 102 to send the MAP SRI may be reception of MAP CANCEL LOCATION. TheHLR 120 may wait until the MAP UPDATE LOCATION from new MSC/VLR 122 iscompleted before handling the MAP SRI message from the CSFB IWF 102.Basically the CSFB IWF 102 may wait for the MAP UPDATE LOCATIONprocedures to complete before sending MAP PRN message to the new MSC/VLR122. The CSMT flag may not be supported by the 2G/3G MSC/VLR andtherefore it may ignore the parameter if received from the UE 108 in theLOCATION UPDATE message. Because of this, the MSC/VLR 122 may releasethe SCCP connection towards the user after completion of location areaupdate procedures. The HLR may send both IMSI and MSISDN in MAP PRNmessage towards CSFB IWF 102. The CSFB IWF 102 on receiving an errorresponse for MAP SRI Request may relay the same in the PRN response tothe HLR 120 for the initial call. The CSFB IWF 102 may include theSuppress T-CSI parameter in the MAP SRI request sent towards HLR 120.The CSFB IWF 102 may ignore substantially all service indications fromthe HLR 120 in the MAP SRI response. If inter-RAT handover from E-UTRAN114 to UMTS/GSM may be supported (i.e., handover of an active packetsession), the MME 126 may interact directly with the SGSN as specifiedin 3GPP TS 23.401. The CSFB IWF 102 may not be involved in theseprocedures. The CSFB architecture may introduce additional post dialdelay compared to a standard CSFB call attempt by invoking a LocationArea Update procedure every time the subscriber is moved from E-UTRAN 14to UTRAN/GERAN. LI for MT calls may be handled at the 2G/3G MSC/VLR 122.In the instances, roaming retry procedures may not be required in thisCSFB IWF architecture.

In some implementations, the MME 126 may send SGsAP-PAGING-REJECTmessage to the CSFB IWF 102 and the corresponding action at CSFB IWF. Ifthe UE 108 is known and is considered to be IMSI attached for EPSservices and “SMS only”, the MME 126 may return an SGsAP-PAGING-REJECTmessage indicating in the SGs cause information element “Mobileterminating CS fallback call rejected by the user”. The CSFB IWF 102 maysend the MAP PRN RESPONSE to HLR 120 with User Error set to “FacilityNot Supported”. If the UE 108 is known and is marked as IMSI detachedfor EPS services or IMSI (implicitly or explicitly) detached for non-EPSservices, i.e., the state of the SGs association is SGs-NULL, the MME126 may return an SGsAPPAGING-REJECT message indicating in the SGs causeinformation element the detach circumstance (“IMSI detached for EPSservices”, “IMSI detached for non-EPS services” or “IMSI implicitlydetached for non-EPS services”). The CSFB IWF 102 may send the MAP PRNRESPONSE to HLR 120 with User Error set to “Unidentified Subscriber”. Ifthe UE 108 is unknown and “MME Reset” is set to “false”, the MME 126 mayreturn an SGsAP-PAGING-REJECT message indicating in the SGs causeinformation element “IMSI unknown. The CSFB IWF 102 may send the MAP PRNRESPONSE to HLR 120 with User Error set to “Unknown Subscriber”. If theUE 108 is unknown and “MME Reset” is set to “true” and is considered tobe IMSI attached for EPS services and “SMS only”, the MME 126 may returnan SGsAP-PAGING-REJECT message indicating in the SGs cause informationelement “Mobile terminating CS fallback call rejected by the user”. TheCSFB IWF 102 may send the MAP PRN RESPONSE to HLR 20 with User Error setto “Facility Not Supported”. The MME 126 may return anSGsAP-UEUNREACHABLE message indicating in the SGs cause informationelement “UE unreachable” if the UE 108 is marked as unreachable, asindicated by Paging Proceed Flag set to “false”. The CSFB IWF 102 onreceiving SGsAP-UE-UNREACHABLE message from MME 126, The CSFB IWF 102may send the MAP PRN RESPONSE message with User Error set to “nosubscriber reply”. The CSFB IWF 102 may transition to the appropriateSGs state based on the reject cause in the Paging Reject message. If theUE 108 fails to find the GERAN/UTRAN radio upon the CS fallback attempt,the call attempt may fail. In this scenario, the HLR 120 may time outwaiting for the PRN response from CSFB IWF 102.

FIG. 4 is a flow diagram 400 illustrating an example method forexecuting a CSFB in accordance with some implementations of the presentdisclosure.

Method 400 begins at step 402 where a PRN request is received from theHLR. For example, the CSFB IWF 102 in FIG. 1 may receive a PRN requestidentifying an MSISDN of the UE 108 from the HLR 120. At step 404, theIMSI and the MSIDN identified by the PRN request are stored. In theexample, the CSFB IWF 102 may store the IMSI and the MSIDN identified bythe PRN request. Next, at step 406, the UE is paged through the MME inan LTE system to update the location through the CS network. As for theexample, the CSFB IWF 102 may transmit a page to the MME 126 for the UE108. In connection with the location update, a cancel location (CL)request is received from the HLR based on assigning a new MSC to the UEat step 408. Again in the example, the HLR 120 may transmit CL requestto the CSFB IWF 102 based on the HLR 120 assigning the MSC/VLR 122 tothe UE 108. At step 410, the stored MSISDN is retrieved from memory.Turning to the example, the CSFB IWF 102 may retrieve the MSISDN frommemory that was identified in the PRN request. Next, at step 412, a MAPSRI request is transmitted to the HLR including the previously-receivedMSISDN. In the example, the CSFB IWF 102 transmits, to the HLR 120, aMAP SRI request including the MSISDN identified in the PRN request. AMAP SRI Ack identifying the current MSRN of the UE is received at step414. Next, at step 416, a PRN Ack identifying the current MSRN istransmitted to the HLR. Yet again returning to the example, the CSFB IWF102 may transmit a PRN Ack including the current MSRN of the UE 108 tothe HLR 120 to terminate the call with the UE 108.

FIG. 5 is a call flow diagram illustrating an embodiment of a newnetwork initiated mobile terminating USSD request/notificationprocedure. USSD is a protocol used by GSM cellular phones to communicatewith the service provider's USSD server. In this scenario, the MSC/VLRthat is executing the fallback is different than the one when the UEfirst falls back to CS. In other words, the MSC changes upon fallbackduring the MT USSD (Unstructured Supplementary Service Data)request/notification procedure. The IWF initiates the fallback as in thecase of an MT call and then acts as the USSD server and delivers theUSSD request/notification to the UE through the HLR and the new MSC. Thecall flow shown in FIG. 5 is also applicable to network initiated MTUSSD notification as well.

Focusing on the call flow portion inside the box, the IWF acts as theUSSD server and sends a MAP (Mobile Applications Part) USSD request tothe HLR. In response, the HLR sends the USSD request to the new MSC/VLR.The new MSC/VLR forwards the USSD request to the UE as per standard CSprocedures and sends the response received from the UE to the HLR. AnUSSD Ack is sent to the HLR by the MSC/VLR in response to receiving theUE's response. The HLR relays the response to the IWF, which furtherrelays the USSD response to the HLR. The HLR then sends a USSD responseto the USSD server or USSD application as the case may be.

FIG. 6 is a simplified block diagram of an exemplary embodiment of acommunication system for a new mobile terminating location report(MT-LR) procedure shown in FIG. 7 and described below. FIG. 6 is similarto FIG. 1 described in detail above. As further shown in FIG. 6, GMLC119 is in communication with the IWF 102 via a 3GPP specified MAP-basedLg interface.

FIG. 7 is a call flow diagram illustrating an embodiment of a new mobileterminating location report (MT-LR) procedure. As before, in thisscenario the MSC/VLR that is executing the fallback is different thanthe one when the UE first falls back to CS. In other words, the MSCchanges upon fallback during the MT-LR procedure. The IWF initiates thefallback to CS as in the case of an MT call. Once the fallbackcompletes, the IWF acts as GMLC and routes the location query to the newMSC by obtaining the new MSC address from the HLR.

Focusing on the call flow portion inside the box, the IWF sends a MAPSRI-LCS (Send Routing Information-Location Services) request to the HLR.The request may identify the subscriber using either IMSI (InternationalMobile Subscriber Identity) or MSISDN (Mobile Station InternationalSubscriber Directory Number) depending on which one is received in theMAP Provide Subscriber Location (PSL) request form the GMLC (GatewayMobile Location Center). In response, the HLR sends a response includingthe network node number (identifying the new MSC) to the IWF. The IWFrelays the MAP PSL received from GMLC to the NW node number returned bythe HLR. The UE location procedure as specified in 3GPP TS 23.271 iscarried out. The MSC/VLR returns a MAP PSL response to the IWF. The IWFthen relays the PSL response to the GMLC.

FIG. 8 is a call flow diagram illustrating an embodiment of a newprovide subscriber information, fallback to CS procedure. The MAPProvide Subscriber Information (PSI) is a commonly used procedure in theCS network where the VLR is queried to provide subscriber location. Asbefore, in this scenario the MSC/VLR that is executing the fallback isdifferent than the one when the UE first falls back to CS.

Focusing on the call flow portion inside the box, the IWF initiates theCS fallback as in the case of an MT call and then upon receiving CancelLocation from the HLR, assumes the role of gsmSCF (GSM Service ControlFunction) and sends an MAP AnyTime Interrogation (ATI) message to theHLR requesting the same set of information that was mentioned in the MAPPSI request message. The information within the response of the MAPAnyTime Interrogation message is then copied into the response of theMAP PSI request message and sent to the HLR thereby completing theprocedure.

The features of the present invention which are believed to be novel areset forth below with particularity in the appended claims. However,modifications, variations, and changes to the exemplary embodimentsdescribed above will be apparent to those skilled in the art, and thedrain assembly described herein thus encompass such modifications,variations, and changes and are not limited to the specific embodimentsdescribed herein.

What is claimed is:
 1. A method comprising: receiving, at an IWF(Internetworking Function) network node, a Mobility Application PartUnstructured Supplementary Service Data (MAP USSD) message identifying aUser Equipment (UE) originated from a USSD application, the UEassociated with a first Mobile Switching Center (MSC); initiatingCircuit Switched Fallback (CSFB) by sending a paging request to the UE;receiving a Cancel Location message associated with the UE from a HomeLocation Register (HLR) indicative of the UE being associated with asecond MSC; forwarding the MAP USSD message to the UE via the HLR andthe second MSC; receiving a MAP USSD response message from the UE viathe HLR; and forwarding the MAP USSD response message to the USSDapplication.
 2. A method comprising: receiving, at an IWF(Internetworking Function) network node, a Mobility Application PartSend Routing Information-Location Services (SRI-LCS) message identifyinga User Equipment (UE) originated from a Gateway Mobile Location Center(GMLC), the UE associated with a first Mobile Switching Center (MSC);initiating Circuit Switched Fallback (CSFB) by sending a paging requestto the UE; receiving a Cancel Location message associated with the UEfrom a Home Location Register (HLR) indicative of the UE beingassociated with a second MSC; forwarding the SRI-LCS message to the UEvia the HLR and the second MSC; receiving a SRI-LCS response messagefrom the HLR; sending a MAP Provide Subscriber Location (PSL) message tothe second MSC; receiving a MAP PSL response message from the secondMSC; and forwarding the MAP PSL response message to the GMLC.
 3. Amethod comprising: receiving, at an IWF (Internetworking Function)network node, a Mobility Application Part Provide Subscriber Information(MAP PSI) message identifying a User Equipment (UE) originated from aHome Location Register (HLR), the UE associated with a first MobileSwitching Center (MSC); initiating Circuit Switched Fallback (CSFB) bysending a paging request to the UE; receiving a Cancel Location messageassociated with the UE from the HLR indicative of the UE beingassociated with a second MSC; sending a MAP Anytime Interrogation (ATI)message to the UE via the HLR and the second MSC; receiving a MAP ATIresponse message from the HLR; and forwarding information in the MAP ATIresponse in an MAP PSI response message to the HLR.